Skip to main content
This forum is closed to new posts and responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:

HCL Software Customer Support Portal for U.S. Federal Government clients
HCL Software Customer Support Portal

Notes/Domino 6 and 7 Forum

Notes/Domino 6 and 7 Forum


  

PreviousPrevious NextNext


~Sanjay Asatumiterjip 9.Sep.03 06:52 PM a Web browser
Domino Server 6.0.2 CF1 Windows 2000


Greetings,

I have searched this forum for this problem before, and implemented the solutions I found, but I am still having the same problem.

Every once in a while (about weekly) my server's nsmtp.exe task pegs at 100% CPU usage. After a few moments QNC.exe runs. I am then unable to QUIT the server or the SMTP task. My only option is to manually end the Domino Server (using Task Manager) and reboot the server.

The server is not overloaded. It usually runs with 90% of the CPU available, and the nsmtp task hardly ever registers a blip on the chart.

After my R6 upgrade, I was experiencing this problem much more frequently, and I added the following INI line, and the problem nearly disappeared.

SMTPNonStandardLineTermination=1

But, still having a weekly server crash is not acceptable. I have learned that when this problem happens, it will usually happen repeatedly. So, when it happens the first time, I make a note of all the current SMTP Connections (IP addresses.) I then restart the server and wait for the nsmtp.exe task to peg the server again. I make another note of the current SMTP connections. There is always a match. So, I block that IP at our firewall, and restart the server again. All is then well until the problem happens again a few days later (with a different offending IP address).

From that behavior, I deduce that there is still a bug in the SMTP routine that locks up the server when a malformed SMTP connection is made. Am I wrong ?

Is there another INI line I can add to prevent the problem? Is there a hotfix available? Will this issue be addressed in 6.0.3.

Plus, I thought I had read that QNC was no longer being used. Did I miss something on my R5 -> R6 upgrade several months ago? Do I need to configure something differently?

I should also note that I am using two DNS Blacklists, Server Mail Rules, and Groupshield, but I don't think those tasks are adding to the problem.

Any ideas ??

David R. Noble






Need help - nsmtp.exe CPU = 100% (~Sanjay Asatumi... 9.Sep.03)
. . Try setting the Pipelining extensio... (~Dan Elhipister... 9.Sep.03)
. . Here's how I fixed nsmtp.exe = 100%... (~Umberto Ekpone... 13.Oct.03)
. . RE: Need help - nsmtp.exe CPU = 100... (~Lorraine Xanhi... 17.Sep.03)





  Document options
Print this pagePrint this page

 Search this forum

  Forum views and search
Date (threaded)
Date (flat)
With excerpt
Category
Platform
Release
Advanced search

 RSS feedsRSS
All forum posts RSS
All main topics RSS